… for Yarn

- Upgraded actions/setup-node from v3 to v4 across multiple workflow files.
- Added a step to enable Corepack for Yarn in the workflows, ensuring compatibility with the package manager specified in the project.

…ld-network/solidity-contracts into feat/testnet4-deployment-support

- Removed comments from .yarnrc.yml to streamline configuration.
- Updated packageManager in package.json to Yarn version 4.12.0 for improved performance and features.

…docs file

- Changed the workflow to use the local path for reusable-solidity-docs.yml instead of the remote repository reference.
- Ensured that both documentation generation and publishing jobs point to the correct local file.

- Remove private key logging from create-operator-keystore and
  get-operator-key; address is sufficient for confirmation
- Remove staking provider and operator private keys from generated
  .env files; keys written to disk are a git-leak risk
- Print staking provider key once to terminal with a prominent
  "copy now" warning instead of persisting it to .env
- Require non-empty password in create-operator-keystore and
  setup-new-staking-provider; empty-password keystores are
  trivially decryptable
- Require explicit keystore path in get-operator-key; remove the
  hardcoded developer-machine UUID default that caused ENOENT for
  all other users
- Fix --list path in get-operator-key: ../../operator-1-keystore
  resolved above repo root; corrected to ../operator-1-keystore
- Convert sync fs calls to fs.promises and add try/catch inside
  main() across all three scripts

…args

Passing --private-key as a CLI argument exposes the key in ps aux
output and persists in shell history. Using ETH_PRIVATE_KEY as an
inline env assignment (ETH_PRIVATE_KEY="$key" cast send ...) keeps
the key out of the argv list.

Introduce _sp_cast_send_ok / _op_cast_send_ok wrappers in
run-new-operator-setup.sh that inject ETH_PRIVATE_KEY for the
respective signer, and replace all --private-key flag usages.

Update fund-new-operator.sh likewise for the deployer key.

Update run-new-operator-setup.sh usage comment to reflect that
NEW_STAKING_PROVIDER_KEY and NEW_OPERATOR_KEY are no longer
written to .env files and must be exported by the operator.

- Drop kind: "transparent" from upgradeProxy options; let the OZ
  plugin infer the proxy type from the deployed proxy admin slot.
  Hardcoding the kind risks a mismatch if the original deploy
  defaulted differently. Add a comment with the cast storage
  command to verify proxy type on-chain.
- Replace two inline const fs = require("fs") declarations with a
  single top-level import * as fs from "fs" to match TypeScript
  conventions and avoid the duplicate binding.

The file was removed in the parent branch commit without explanation.
Downstream consumers relying on deployments/mainnet/TokenStaking.json
break silently without it. Restored from the last known-good version
(commit ab29e02).

approveApplication already checks application != address(0) but
increaseAuthorization did not. The APPROVED status check provides
a functional backstop, but adding the explicit guard makes the
invariant consistent across both entry points.

…ld-network/solidity-contracts into feat/testnet4-deployment-support

- Added validation to ensure ETH_PRIVATE_KEY is set before sending transactions.
- Introduced a mechanism to prevent overwriting the deployer key with stale values from environment files.
- Updated the script to maintain the correct private key for the contract owner during operator setup.

- Updated prerequisites for deploying operators to include AUTO_FUND_T for automatic minting of T tokens.
- Added a function to compute T token shortfall and validate the deployer's balance.
- Implemented error handling for insufficient T balance and ensured proper private key management for minting.
- Introduced normalization for addresses to improve consistency in key comparisons.

- Removed specific ignore rules for deployments in .gitignore to allow for better management of deployment files.
- Added new deployment files for Sepolia, including .chainId, NuCypherToken.json, T.json, TokenStaking.json, and VendingMachineNuCypher.json, to support the latest contract deployments.
- Enhanced the operator setup script to improve handling of ETH funding for new operators, including adjustable parameters for ETH allocation and better error handling for deployment paths.
- Updated prerequisites and usage instructions in the setup script for clarity and improved user experience.

- Updated contract addresses and transaction hashes in deployment files for NuCypherToken, T, TokenStaking, and VendingMachineNuCypher to reflect the latest deployments on Sepolia.
- Enhanced the operator setup script with new functions for computing ETH shortfalls and converting values to decimal, improving error handling for deployer funding requirements.
- Added checks to ensure the deployer has sufficient ETH for operator bootstrap, enhancing the robustness of the deployment process.